-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update I/O threads documentation #222
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Uri Yagelnik <[email protected]>
Co-authored-by: Madelyn Olson <[email protected]> Signed-off-by: uriyage <[email protected]> Signed-off-by: Uri Yagelnik <[email protected]>
Co-authored-by: Madelyn Olson <[email protected]> Signed-off-by: uriyage <[email protected]> Signed-off-by: Uri Yagelnik <[email protected]>
Signed-off-by: Uri Yagelnik <[email protected]>
7c0dc4a
to
d3024f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ranshid Was there anything else you identified that needed to get fixed?
|
||
### Limitations | ||
|
||
I/O threading is currently not supported with TLS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good that this is removed. It could be worth mentioning that it IS supported since 8.0 too, since users may remember that it wasn't supported in the past.
In another PR we can add some dedicated page for IO threading?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Should we add a dedicated page about I/O threading next?
In the issue, I also mentioned these: faq.md:
latency-monitor.md:
|
Update IO threads documentation.
#196